System and method for tokenizing offers

ABSTRACT

Aspects of the present disclosure involve systems, methods, devices, and the like for tokenizing offers. The current disclosure presents a system and method that can present a tokenized offer for saving and retrieving from a digital wallet. The tokenized offer may be presented on a client site for selection by a user interested in taking advantage of the promotion without having to leave the current site. The current disclosure also presents a system that can retrieve the tokenized offer saved for use with a purchase. The tokenized offer may be automatically applied and on display at the merchant site and/or retrieved from the digital wallet.

TECHNICAL FIELD

The present disclosure generally relates to communications betweendevices, and more specifically, to the communication between devices forreceiving tokenized offers.

BACKGROUND

Rapid advancements in technology and communications have led to theubiquitous use of wireless electronics. As such, today's society hasgrown to become heavily device reliant, with a need to be constantlyconnected. This reliance has led to the use of electronics to makemonetary transactions for goods and services.

For example, consumers can now go to a home computer to purchase an itemat an online store site. In some instances, the user can obtain specialoffers and promotions from these online stores while browsing adifferent site. Unfortunately, conventional systems generally requirethe user to leave the current site in order to obtain and use thepromotion. However, a user may have an interest in remaining on thecurrent site to continue reading, browsing, streaming, or otheractivity, at the moment. Thus, the promotion presented to the user, maybe lost and possible sale for the merchant postponed or not completed.This loss of sale, offer, or promotion can lead to a loss of time (ifredirected), money, as well as stress and frustration to a user.Therefore, it would be beneficial if a system were created that providesuser with the ability to store and access such promotions at a latertime.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a block diagram of a first user receiving an offerwhile interacting with one or more devices.

FIG. 2 illustrates a block diagram of a system for tokenizing offers.

FIGS. 3A-3D illustrate a communication with a user device for obtainingtokenized offers.

FIG. 4 illustrates a block diagram of communication between devices fortokenizing offers.

FIG. 5 illustrates a flow diagram for tokenizing offers.

FIG. 6 illustrates an example block diagram of a computer systemsuitable for implementing one or more devices of the communicationsystems of FIGS. 2 and 5.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereasshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

In the following description, specific details are set forth describingsome embodiments consistent with the present disclosure. It will beapparent, however, to one skilled in the art that some embodiments maybe practiced without some or all of these specific details. The specificembodiments disclosed herein are meant to be illustrative but notlimiting. One skilled in the art may realize other elements that,although not specifically described here, are within the scope and thespirit of this disclosure. In addition, to avoid unnecessary repetition,one or more features shown and described in association with oneembodiment may be incorporated into other embodiments unlessspecifically described otherwise or if the one or more features wouldmake an embodiment non-functional.

Aspects of the present disclosure involve systems, methods, devices, andthe like for tokenizing offers. In one embodiment, a system isintroduced that can present a tokenized offer for saving and retrievingfrom a digital wallet. The tokenized offer may be presented on a clientsite for selection by a user interested in taking advantage in thepromotion without having to leave the current site. The tokenized offermay be presented in response to a verification that a customer meetsrestrictions and/or criteria set by a merchant. In another embodiment, asystem is introduced that can retrieve the tokenized offer saved for usewith a purchase. The tokenized offer may be automatically applied and ondisplay at the merchant site and/or retrieved from the digital wallet.

Rapid advances in communications have made portable electronic devices,such as smartphones and tablets, part of everyday life. Among otherthings, these electronic devices can be used to browse the web andpurchase goods and services. In some instances, the user may user theelectronic device to browse the web or stream video, while in otherinstances, the user may be specifically looking to purchase an item.Oftentimes, however, a promotion for an item may appear at aninopportune time, when the user in not specifically searching andinstead reading an article. In these instances, the user may find itdifficult to leave the current site in order to take advantage of thecurrent promotion presented.

An example of this is illustrated in FIG. 1, where a user 104 isinteracting with a user device 102. In particular, FIG. 1 illustrates ablock diagram 100 of a user 104 receiving an offer 106 while interactingwith one or more devices 102. The user device 102 can be a smart phone,tablet, laptop, and other electronic device that may be used forcommunicating, browsing, purchasing, and the like.

For illustration purposes, a user 104 is presented interacting with auser device 102, engaged in learning how to create a blog from a site108. The site 108 may include user profile information (e.g., user nameand picture), instructions, and other details relevant to the currentsite 108 visited. In addition, the site 108, may also includeadvertisements, news articles, and even offers and promotions in theform of a coupon 106. The coupon may be available for use at a differentsite, with another merchant, after a purchase, etc. Oftentimes, to takeadvantage of the coupon, the user will be redirected to another sitecorresponding to the entity offering the discount. As illustrated inFIG. 1, the coupon 106 may be accompanied with a button 110 forredirecting the user 104. However, as indicated, the user may be in themiddle of learning a new skill set (e.g., learning how to create a blog)and may not be not interested in leaving the current site. Thus, theuser 104 may be left with a decision to forgo the saving presented inorder to continue on the current site 108. Therefore, in order toeliminate the need to relinquish such promotion, tokenized offers areintroduced that can provide a system and method for saving and accessingsuch coupon 110 at a later time.

In the current embodiment, a system is presented that is able tocommunicate with a client member offering the promotion to generate atokenized offer for later use. The tokenized offer is stored using atoken that may be generated in response to an offer acceptance by theuser and available for accessing, viewing, and using at a later time. Inone embodiment, the tokenized offer may be saved to a digital walletand/or with a payment provider for later use.

FIG. 2 is a block diagram of a networked system 200 for implementing theprocesses described herein, according to an embodiment. In particular,FIG. 2 illustrates a block diagram of a system 200 for tokenizingoffers. System 200 illustrates at least some of the interactions betweenmultiple entities and/or devices for the authentication, use andpurchase of a product or service with a merchant in association with aservice provider. As shown, system 200 may include or implement aplurality of devices, computers, servers, and/or software componentsthat operate to perform various methodologies in accordance with thedescribed embodiments. It will be appreciated that the devices,computers, and/or servers illustrated in FIG. 2 may be deployeddifferently and that the operations performed and/or the servicesprovided by such devices, computers, and/or servers may be combined orseparated for a given embodiment and may be performed by a greaternumber or fewer number of devices, computers, and/or servers.Furthermore, one or more of the devices, computers, and/or servers maybe operated and/or maintained by the same or different entities.

System 200 includes a merchant device 202, a primary user device 224(e.g., primary device/trusted primary device 102), a third-party serviceprovider computer 212, and a secondary user device 236 (e.g., secondarydevice 104) in communication over a network 250. The merchant device202, primary user device 224, third-party service provider computer 212,and the secondary user device 236 may each include one or moreprocessors, memories, and other appropriate components for executingcomputer-executable instructions such as program code and/or data. Thecomputer-executable instructions may be stored on one or more computerreadable mediums or computer readable devices to implement the variousapplications, data, and steps described herein. For example, suchinstructions may be stored in one or more computer readable media suchas memories or data storage devices internal and/or external to variouscomponents of system 200, and/or accessible over network 250.

The merchant device 202 may be implemented as a communication devicethat may utilize appropriate hardware and software configured for wiredand/or wireless communication with the primary user device 224,third-party service provider computer 212, and/or secondary user device236. For example, the merchant device 202 may be implemented as apersonal computer (PC), a smart phone, laptop/tablet computer,point-of-sale device, wristwatch with appropriate computer hardwareresources, eyeglasses with appropriate computer hardware, other type ofwearable computing device, implantable communication devices, and/orother types of computing devices capable of transmitting and/orreceiving data. The merchant device 202 may correspond to and beutilized by a user, such as an employee of a merchant and/or anotherperson authorized by the merchant.

The merchant device 202 may include one or more payment applications204, other applications 206, a database 208, and a network interfacecomponent 210. The payment applications 204 and other applications 206may correspond to executable processes, procedures, and/or applicationswith associated hardware. In other embodiments, merchant device 202 mayinclude additional or different components having specialized hardwareand/or software to perform operations associated with the paymentapplications 204 and/or the other applications 206.

The payment application 204 may facilitate financial transactionscorresponding to the sale of goods and/or services offered by themerchant. For example, the payment application 204 may provide aninterface for customers to purchase the goods or services and to receivecustomer payment information (e.g., customer credit card information).The payment application 204 may further transmit customer paymentinformation to a payment processor (e.g., such as a payment processorcorresponding to the third-party service provider computer 212 or thesecondary user device 236) to process the customer payment information.The payment application 204 may also facilitate other types of financialtransactions such as banking, online payments, money transfer, discountcoupon information, and/or the like.

The merchant device 202 may execute the other applications 206 toperform various other tasks and/or operations corresponding to themerchant device 202. For example, the other applications 206 may includesecurity applications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 250, or othertypes of applications. The other applications 206 may also includeadditional communication applications, such as email, texting, voice,and instant messaging (IM) applications that enable a user 106 to sendand receive emails, calls, texts, and other notifications through thenetwork 250. In various embodiments, the other applications 206 mayinclude location detection applications, such as a mapping, compass,and/or global positioning system (GPS) applications, which may be usedto determine a location of the merchant device 202. The otherapplications may 206 include social networking applications.Additionally, the other applications 206 may include device interfacesand other display modules that may receive input and/or outputinformation. For example, the other applications 206 may include agraphical user interface (GUI) configured to provide an interface to theuser.

The merchant device 202 may further include a database 208, which may bestored in a memory and/or other storage device of the merchant device202. The database 208 may include, for example, identifiers (IDs) suchas operating system registry entries, cookies associated with thepayment application 204, tokens, encryption keys, and/or otherapplications 206, IDs associated with hardware of the network interfacecomponent 210, IDs used for payment/user/device authentication oridentification, and/or other appropriate IDs. The database 208 may alsoinclude information corresponding to one or purchase transactions ofcustomers who have purchased goods or services from the merchant,browsing histories of the customers, or other types of customerinformation. In certain embodiments, the merchant device 202 may alsoinclude information corresponding to payment tokens, such as paymenttokens generated by the third-party service provider computer 212 and/orgenerated by the secondary user device 236.

The merchant device 202 may also include at least one network interfacecomponent 210 configured to communicate with various other devices suchas the primary user device 224, the third-party service providercomputer 212, and/or the secondary user device 236. In variousembodiments, network interface component 210 may include a DigitalSubscriber Line (DSL) modem, a Public Switched Telephone Network (PTSN)modem, an Ethernet device, a broadband device, a satellite device and/orvarious other types of wired and/or wireless network communicationdevices including microwave, radio frequency, infrared, Bluetooth®,Bluetooth low-energy, near field communication (NFC) devices, and/or thelike.

The third-party service provider computer 212 may be maintained, forexample, by a third-party service provider, which may provide paymentprocessing services for the merchant. In one example, the third-partyservice provider may be provided by PAYPAL®, Inc. of San Jose, Calif.,USA. Alternatively, the third-party service provider computer 212 may beassociated with a user of the primary and secondary device 224, 236. Assuch, the third-party service provider computer 212 includes one or morepayment processing applications 214, which may be configured to processpayment information received from the merchant device 202 or from aselection at the primary or secondary user device 224, 236. For example,the payment application 204 of the merchant device 202 may receivepayment information from a customer to purchase a service or goodoffered by the merchant. Upon receipt of the payment information, thepayment application 204 may transmit the payment information to thethird-party service provider computer 212. The payment processingapplication 214 of the third-party service provider computer 212 mayreceive and process the payment information. As another example, thepayment application 204 can present a payment code on a display of theuser device associated with the merchant. The payment code can bescanned or transmitted to the merchant device 202 for paymentprocessing.

The third-party service provider computer 212 may execute the otherapplications 216 to perform various other tasks and/or operationscorresponding to the third-party service provider computer 212. Forexample, the other applications 216 may include security applicationsfor implementing client-side security features, programmatic clientapplications for interfacing with appropriate APIs over the network 250,or other types of applications. The other applications 216 may alsoinclude additional communication applications, such as email, texting,voice, and IM applications that enable communication of emails, calls,texts, and other notifications through the network 250. In variousembodiments, the other applications 216 may include location detectionapplications, such as a mapping, compass, and/or GPS applications, whichmay be used to determine a location of the third-party service providercomputer 212. Additionally, the other applications 216 may includedevice interfaces and other display modules that may receive inputand/or output information. For example, the other applications 216 mayinclude a GUI configured to provide an interface to one or more users.

The third-party service provider computer 212 may further include adatabase 218, which may be stored in a memory and/or other storagedevice of the third-party service provider computer 212. The database218 may include, for example, IDs such as operating system registryentries, cookies associated with the payment processing application 214and/or other the applications 216, IDs associated with hardware of thenetwork interface component 222, IDs used for payment/user/deviceauthentication or identification, and/or other appropriate IDs.

According to a particular embodiment, the third-party service providercomputer 212 may include a set of payment profiles 220 corresponding topast sales transactions executed by the merchant device 202 with respectto one or more customers of the merchant. Alternatively, the third-partyservice provider computer 212 may include a set of merchant paymentprofiles corresponding to the payment sources associated to acorresponding merchant. For example, a particular payment profile fromthe set of payment profiles 220 may include payment informationcorresponding to a particular customer of the merchant and/or a merchantassociated with a user. The payment information may include credit cardinformation (e.g., card number, expiration date, security code, cardissuer, and/or the like), Automated Clearing House (ACH) information(e.g., account number, routing number, and/or the like), identificationinformation associated with the particular customer/user (e.g., acustomer identifier, name, address, phone number, date of birth, and/orthe like), billing information, and/or any other type of paymentinformation associated with the particular customer. Furthermore, otherpayment profiles of the set of payment profiles 220 may include paymentinformation corresponding to other customers of the merchant and/orother merchants associated with the user. In addition, the third-partyservice provider computer 212 may store the set of payment profiles 220according to a first file format.

The third-party service provider computer 212 may also store a set ofpayment tokens corresponding to the set of payment profiles 220. Forexample, each payment profile of the set of payment profiles 220 may beassociated with a corresponding payment token from the set of paymenttokens. In some embodiments, each payment profile may include acorresponding payment token from the set of payment tokens. The set ofpayment tokens may be particular to the third-party service providercomputer 212 (e.g., computers from other service providers may be unableto use the set of payment tokens) and may enable the merchant device 202to more securely process payment transactions with the third-partyservice provider computer 212. For example, in order to process apayment transaction that involves a credit card number associated with aparticular payment profile, the third-party service provider computer212 may provide the merchant device 202 with a particular payment tokenthat is different from the credit card number. The merchant device 202may use the particular payment token to process the payment transactioninstead of the credit card number. Further, the merchant device maystore and associate the particular payment token with the particularpayment profile instead of the credit card number, thereby protectingthe credit card number from being stolen in a potential security breachof the merchant device 202.

In various embodiments, the third-party service provider computer 212also includes at least one network interface component 222 that isconfigured to communicate with the merchant device 202, the primary userdevice 224, and/or the secondary user device 236 via the network 250.Further, the network interface component 222 may comprise a DSL modem, aPSTN modem, an Ethernet device, a broadband device, a satellite deviceand/or various other types of wired and/or wireless networkcommunication devices including microwave, RF, and IR communicationdevices.

The primary user device 224 may be implemented as a communication devicethat may utilize appropriate hardware and software configured for wiredand/or wireless communication with the merchant device 202, third-partyservice provider computer 212, and/or the secondary user device 236. Theprimary user device 224, may be a personal computer (PC), a smart phone,laptop/tablet computer, wristwatch with appropriate computer hardwareresources, eyeglasses with appropriate computer hardware (e.g. GOOGLEGLASS®), other type of wearable computing device, implantablecommunication devices, and/or other types of computing devices capableof transmitting and/or receiving data. In one embodiment, the primaryuser device 224 may be mobile device 102 communicating with seconddevice 104, a merchant device and/or service provider 212.

The primary user device 224 may include a payment processing application226 that may be used as a digital wallet that can communicate with amerchant device 202, secondary user device 236, and/or third partyservice provider 212 for purchasing and transacting. The paymentprocessing application 226, can work jointly with database 230 forretrieving bank account information, user accounts, security codes,tokens that may be associated with various merchant locations.Similarly, the payment processing application, can also provide accessto the user profiles for determining which payment method, processingcode, to use at a merchant location. The primary user device 224 mayinclude an enclave 232 which can be a secure hardware level storage aredesignated for the payment processing application 226. The enclave 232can enable the storage of private and public keys and a randomlygenerated token that enables the secure communication and validation ofthe user of the payment processing application with the third partyservice provider 212.

In one embodiment, the primary device 102 uses a private key and securetoken encryption for communicating with the payment processingapplication 226. The secure token can be pushed in a silent tone in anout of band notification between the payment processing application(e.g., PayPal application) and a server. In other words, when thepayment processing application 226 is first installed, two keys aregenerated, a private key and a public key. The private key is put in thesecure enclave 232 and the public key is sent to the database 218 orother server associated with the third-party service provider 212.Therefore, when a user associated with the primary user device 224,first logs into the payment processing application 226, if the login issuccessful a server associated with the third-party service provider 212or even a merchant device 202 initiates a silent tone notification tothe payment processing application 226. The push notification can be anout-of-band notification which ensures a secure access through the useof the silent tone notification including the transmission of a token.Thus, a request for access from the payment processing application 226,should include the token encrypted which can be decrypted with thepublic key that was originally transmitted.

The primary user device 224 may also include other applications 228 toperform various other tasks and/or operations corresponding to theprimary user device 224. For example, the other applications 228 mayfacilitate communication with the merchant device 202, such as toreceive an indication, from the merchant device 202, to switch paymentprocessing services from the third-party service provider to the serviceprovider. As another example, the other applications 228 may includesecurity applications, application that enable designation of a primaryinteractive device, and applications that allow for web site searches(including access to merchant websites). The other applications 228 mayalso include additional communication applications, such as email,texting, voice, and IM applications that enable communication of emails,calls, texts, and other notifications through the network 250. Invarious embodiments, the other applications 228 may include locationdetection applications, such as a mapping, compass, and/or GPSapplications, which may be used to determine a location of the userdevice 224. The other applications may 228 social networkingapplications. Additionally, the other applications 228 may includedevice interfaces and other display modules that may receive inputand/or output information. For example, the other applications 228 mayinclude a GUI configured to provide an interface to one or more users.

The primary user device 224 may further include a database 230, whichmay be stored in a memory and/or other storage device of the primaryuser device 224. The database 230 may include, for example, identifiers(IDs) such as operating system registry entries, cookies associated witha web browser and/or the other applications 228, IDs associated withhardware of the network interface component 234, IDs used forpayment/user/device authentication or identification, bank information,merchant information, user accounts, and/or other appropriate IDs. Inaddition, the database 230 may include user identifier information whichcan be used in conjunction with secondary user device 236 during anexplicit code exchange and/or contextual information for web browserauthentication.

Primary user device 224, can also be equipped with various sensors 234to provide sensed characteristics about the primary user device 224 andits environment. For example, the sensors 234 can include a camera fortaking images of the surroundings used to determine the information toprovide a user. As another example, the sensors 234 can includemicrophones for receiving audio signals, which can be used to detectlocation, and other relevant terms that may be spoken. Further, thesensors 234 can include an accelerometer, a light sensor, a biometricsensor, temperature sensor, etc. For example, the biometric sensor canbe used to collect a user fingerprint scan. Each type of sensorproviding various characteristics about the device, user, orenvironment.

The primary user device 224 may also include at least one networkinterface component 110 configured to communicate with various otherdevices such as the merchant device 202, the third-party serviceprovider computer 212, and/or the secondary user device 236. In variousembodiments, network interface component 234 may include a DigitalSubscriber Line (DSL) modem, a Public Switched Telephone Network (PTSN)modem, an Ethernet device, a broadband device, a satellite device and/orvarious other types of wired and/or wireless network communicationdevices including microwave, radio frequency, infrared, Bluetooth®,Bluetooth low-energy, near field communication (NFC) devices, and/or thelike.

As indicated above, a secondary user device 236 (e.g., secondary device104) may be presently available and used by a consumer (e.g., user 106).The secondary user device 236, much like the primary user device may beequipped with payment processing applications 238 as well as otherapplications 240. The payment processing applications 238 and otherapplications 240 may be used to perform various tasks and/or operationscorresponding to the secondary user device 236. The other applications228 may include additional communication applications, such as email,texting, voice, and IM applications that enable communication of emails,calls, texts, and other notifications through the network 250. Inaddition, the other applications 228 may include location detectionapplications, such as a mapping, compass, and/or GPS applications, whichmay be used to determine a location of the secondary user device 236.The other applications may further include 228 social networkingapplications and device interfaces and other display modules that mayreceive input and/or output information

For example, the applications 238, 240 may facilitate communication withthe merchant device 202, such as by presenting a QR code that may beused for making a purchase. As another example, the applications 238,240 may provide notice of an incoming call or text to the user 106 ofthe secondary user device 236. Still as another example, theapplications 238,240 can provide details and/or login information forauthentication by the primary user device 224, with a merchant device202, or third-party service provider 212.

The secondary user device 236 may also include a network interfacecomponent 242 for connecting and interacting with at least primary userdevice 224, merchant user device 202, and/or third-party serviceprovider computer 212 over network 250. The network interface component242 may comprise a DSL modem, a PSTN modem, an Ethernet device, abroadband device, a satellite device and/or various other types of wiredand/or wireless network communication devices including microwave, RF,and IR communication devices.

The network 250 may be implemented as a single network or a combinationof multiple networks. For example, in various embodiments, the network250 may include the Internet or one or more intranets, landlinenetworks, wireless networks, and/or other appropriate types of networks.Thus, the network 250 may correspond to small scale communicationnetworks, such as a private or local area network, or a larger scalenetwork, such as a wide area network or the Internet, accessible by thevarious components of system 200.

In addition, the secondary user device 236 can also include sensors 244that may be used for providing measured information about the user,device, location, environment, etc. The sensors can be used to detectlight (is device in a pocket), biometric data (is user working out),location (user is in a meeting, call received), etc. Further, thesensors 244 can also be used to determine proximity between devices andlocation of interest as well as determine processor usage and/or signalstrength relative to other devices including primary user device 224,third party service provider computer 212, and merchant device 202.

Further, system 200 can also include a communication between thesecondary user device 236 and/or primary user device 224 withthird-party service provider computer 212 for saving and retrievingoffers tokenized and stored for later use. To illustrate thiscommunication, FIGS. 3A-3D are presented where a user device 102 used inobtaining tokenized offers. As an example, a third party serviceprovider (e.g., PayPal) will be used store and retrieve the offers. Inaddition, various offers from numerous merchants will be describedhowever, the details are not so limited as other merchants, websites,discounts, promotions, and service providers may be contemplated.

FIG. 3A begins with an illustration of a user 102 browsing a site 302that describes how to create a blog. The site 302 can include, amongother things, instructions, user profile information, file history,contact information, etc. Additionally, the site 302 can includeadvertisements, promotions, coupons, and other offers 304 available forthe user 104 to utilize. As example, FIG. 3A illustrates a user 104browsing site 302 and in particular, user 104 reading an article oncreating a blog. During the preview, an offer from a merchant (e.g.,East) presenting a coupon 304 with a discount and/or free shipping whena purchase is made.

Note that unlike a conventional system (as illustrated in FIG. 1),coupon 304 presents the user with the option to “Add to Wallet,” or“Save to Wallet.” In the current embodiment, the Add to Wallet optionenable a user to save the promotion for later use. That is to say,unlike conventional systems where the promotion presented is for use atthe moment and re-routes the user to a new site, coupon 304 insteadenables continual browsing of the current site 302 while saving thecoupon 304 for later use.

FIG. 3B, presents the payment provider site 304 where a user 104 canretrieve a coupon 304 that was added to wallet at an earlier point intime. As an example, a user 104 is logged into his/her PayPal creditsite 306, where in addition to the user information including balance,available credit, etc., the site also illustrates the available couponsthe user has added and are available for use. In this instance, the user104, who was earlier reading about blogging can now retrieve thecoupon(s) 304. Upon logging into and/or authenticating at the providersite, as illustrated in FIG. 3B, the save coupon 304 is presented andavailable for the user. Note that in some instances, the saved coupons304 may be available on the home site of the provider, in a coupontab/founder, etc.

At FIG. 3C, an illustration is given of a user 104 is ready and able touse the saved coupon 304. In particular, FIG. 3C is illustrated where auser 104 is at the merchant site (e.g., East) 310 for purchasing aproduct. As an example, the user 104 has an interest in purchasing apair of pants and has been offered free shipping 312 as available onwith the saved coupon 304. Note that the merchant site may be visitedthrough the merchant application, via retrieval of the site 310 using aninternet service provider, or via the selection of the saved coupon 304from the provider site 306.

Now turning to FIG. 3D, the provider site 306 is again illustrated whereother offers 356 are available and presented to the user 104 forselection and later use. Note that although the offer was presented tothe user 104 from a site 302 while the user 104 was browsing, otheroffers may be available on a digital wallet, from a service providerapplication, from a merchant site, as well as other sites including butnot limited to news sites, learning sites, during video streaming, froma social networking site, etc. In addition, note that the offers 304 areretrievable from any user device including but not limited to a smartphone, tablet, home computer, wearable device, etc.

FIG. 4 illustrates a timing diagram 400 of the interactions between aclient and the service provider for the presentation and storage of atokenized offer. In FIG. 4, the presentation of a tokenized offer thatmay be presented to a user 104 and added to a wallet is illustrated. Tobegin the presentation, a client 402 initiates a communication with aserver for an offer related token request 416. In one exemplaryembodiment, a client (e.g., East) contacts the payment service provider(e.g., PayPal) for the opportunity to present the offer. The initialcontact can include a request for a token 416. In response to therequest 416, the server 404 can communicate with a secondary customerservice provider 406 or customer service entity, data structure,database or the like, for the verification 418 that the client 402 is anexisting customer 418. Additionally, customer verification may alsooccur at verification 418. During this verification, a merchantsrestrictions and clients information may be checked to ensure thatmerchant preferences are met and the customer (e.g., user 104) should beprovided with the offer. That is to say, a check on whether the customeris an appropriately targeted customer. For example, a merchant may havea restriction indicating the preference for customers under 25 yearsold. Verification of customer age may occur prior to offering the token.In addition, a verification that the customer is a customer of thepayment provider (e.g., PayPal customer) may occur as well as check forany outstanding risk warnings with the payment provider. Further, acheck of customer cookies for relevant advertisements, search historyand/or profile information, relationships, and communication on otherrelated applications (e.g., social media) can be considered forverification of the customer.

Once the customer service entity 406 confirms the customer/merchant, thepayment provider (e.g., server 404) can grab the offer details 420, thatwill be surfaced to the customer via the client site. For example, thecoupon that will be presented on the news site visited by the customer.The offer details may be obtained from a separate entity, offersservice, or campaign service entity 408. Note that the offer serviceentity 408 may be a separate system, data structure, database, or thelike. The offer details can include the offer identification number, themonetary amount to be discounted, the underwriter (e.g., who pays forthe offer—payment provider, merchant, etc.), offer dates, expiration,etc. In addition, if the merchant has a campaign or other relationshipwith the payment provider server 404. The relationship can include aretainer amount that may be provided from the merchant to the paymentprovider for the use when presenting the offers to the customers. Forexample, a merchant can provide a payment provider like PayPal with anupfront monetary amount of $500 to surface the offers to customers. Eachtime a customer clicks on the save to wallet button, a designated amountis pulled from that account. If the offer is used then the funds areused, else if the offer is not used and/or expires then the funds can bereturned for use with another customer. Alternatively, if anagreement/campaign does not exist, the payment provider, merchant, orother financial institution may front a percentage or the full amount ofthe offer.

The designated amount that is pulled from the campaign amount isconfirmed available and updated when the offer 422 is presented to thecustomer 422. In one embodiment, the offer is presented and pushed bythe client 402. However, in some instances the offer may be pushed bythe merchant, social media site or by other site of relevance to thecustomer. As illustrated in FIG. 4, one the offer details are verified,the offer is displayed 422 on the client site and if desired by thecustomer a button clicked 424 (e.g., “Save to Wallet”).

A customer (e.g., user 104) interested in the offer through the use ofthe clicked button 424 will then initiate a communication between theserver 404 and the offer services entity 408 for the update of funds426. The update of funds can include a reduction in the monetary amountheld in the campaign amount, an update in a service provider or merchantaccount (if the amount is fronted by the provider and/or merchant), etc.

Once the funds have been updated, the server 404 can respond to theclient 402 with a tokenized offer. The offer along with offer detailscan be stored in a digital wallet in the user device 102, an internal orexternal storage unit, and/or other component from which the offerdetails can be retrieved from. If the customer is a customer of thepayment provider (e.g., PayPal user), then the offer can be saved to thePayPal wallet and/or local data storage for local search. Alternatively,the offer can be saved to a local data storage for use and retrievalwithout the need to be a client, customer, or affiliated with a specificfinancial institution, payment provider, and/or merchant. Included inthe token offer can be the offer details, expiration date, merchant,authenticating information, and other relevant information.

Once the offer token is transmitted 428 to the client, priorityinformation is kept in the server 404 and may be stored in a separateentity such as a date priority queue 410. The data priority queue 410may prioritize the token and keep track of the corresponding expirationdates. For example, if a token to East is approaching expiration in twodays, the customer 414 may be sent emails 432 updating on the soonexpiring token. In some instance, in addition to or instead of an emailnotification, a message, a customized push notification from themerchant 414 and/or the payment provider server 404 (i.e., client and/orPayPal is notified that an offer for a client is soon expiring), anupdate from the client site, or the like may be sent as a reminder. Inone embodiment, the offer may be a short timed offer which can includecontinuous or interval notifications to the customer 414 via the clientsite 402 (not shown). For example, a customer 414 may be presented withan offer that has a 30 minute life, notifications may appear asreminders on the client site as the user continues to browse. If thetoken expires and it was part of a campaign or other agreement, thefunds originally pulled for the token may be returned for use withanother token offer.

At a later instance, when the user 104 is ready to use the offer, theuser 104 (customer 414) may visit the merchant site or open theirdigital wallet, PayPal app, or other where the offer may be retrieved.In one embodiment, the user may open up the merchant site and the offermay be automatically applied to the purchase at checkout. In anotherembodiment, when the customer arrives at the merchant's website, abanner, overlay, or notification can pop up reminding the customer tosave the offer or that a saved offer is pending and ready to be used.Upon use of the offer, if the merchant 412 is tied to a campaign orother agreement with the payment provider, the offer amount may bereduced from the account or retainer amount. (not shown)

Note that the offers may be surfaced within any web experience, thusanywhere where an advertisement may exist, an offer may similarly existthat may be saved to a wallet. In addition, the offers are alsoavailable and applicable to the account at checkout. A rebate may alsobe presented with money back with purchase. Note that an offer may beprovided to any user 104 without the need for a specific membership withthe financial institution. In some embodiments, a user may checkout withretrieval of the offer that may be stored locally on the user device102. Alternatively, the user 104 may user the offer after confirmationof membership with the financial institution or payment provider. If theuser 104 is not a member, onboarding may be initiated at checkout.

FIG. 5 illustrates example process 500 for implementing a system thatprovides tokenized offers as computing system 200 of FIG. 2 and/ortiming diagram 400 of FIG. 4. In particular, FIG. 5 illustrates a flowdiagram illustrating operations for verifying and presenting a customerwith a tokenized offer over a client site for saving to a digitalwallet. According to some embodiments, process 500 may include one ormore of operations 502-518, which may be implemented, at least in part,in the form of executable code stored on a non-transitory, tangible,machine readable media that, when run on one or more hardwareprocessors, may cause a system to perform one or more of the operations502-518.

Process 500 may begin with operation 502, where a system such a paymentprovider system and server receive a request for an offer from a clientsystem for an associated site. The offer request received at the servermay be affiliated with a merchant, service provider, charity,non-profit, or the like. The offer may come in the form of a couponpresented on the client site for promotions, rebates, discounts,incentives, points, rewards, etc. for use the a user at the merchant.

Once the request is received, the server may communicate with anothersystem, entity, database, data structure or service for the verificationof information. The information verification can include verification ofthe merchant information and customer information. Among other checks,the customer may be checked to verify that merchant restrictions aremet, risks are checked, user preferences, search history, and socialrelationships are checked. The checks can help indicate whether thecustomer is a good candidate to who the offer should be presented.

If the customer does not meet the predefined restrictions set by themerchant at operation 504, then the offer request may be denied. Adenied offer indicates to the client that the offer request may not befulfilled and the site should not present this offer to the customer. Inone embodiment, if the customer does not meet the predefinedrestrictions, other types of advertisements and even promotions maycontinue to be displayed on the client site. For example, a customer maybe presented with advertisements and even offers that may not includerestriction checks or include other restrictions that the currentcustomer meets. Alternatively, if all checks/restrictions are met, thenan offer may be displayed on the client site. An exemplary restrictionset by the merchant may be age, as the merchant may be targeting anolder audience.

At operation 510, a tokenized offer is present on the client site forselection by the user of the user device. Prior to the presentation ofthe offer, the server may collect offer information (e.g., savings,type, expiration, etc.) as well as check for any associatedrelationships, campaigns and agreements established by the merchant andthe server. If a retainer exists, a predefined amount may be deductedfrom the account to account for the offer discounts. In some instances,a campaign may not exist in which case the offer amount may be paid forby the server in its entirety or partially as an agreement with themerchant. Further, the tokenized offer may be stored locally in the userdevice and in a digital wallet affiliated with the server, paymentprovider, financial institution, merchant, etc. Note that in someinstances, the predefined amount may not be deducted until operation516.

Upon presentation of the tokenized offer to the customer, the customerthen has the opportunity to save to wallet. Wishes to forgo the offer,then the offer is not saved. In instances, where the offer is affiliatedwith a campaign, the monetary amount pulled from the account may bereimbursed for use with another offer. If, however, the user desires touse the offer and selects the button presented to save to wallet, thenprocess 500 continues to operation 516. At operation 516, a token isgenerated for the offer for later retrieval (locally or remotely throughdigital wallet) and is prioritized by the server at operation 518. Also,at operation 516 if a retainer exists, a predefined amount may bededucted from the account to account for the offer discounts. In oneembodiment, the token generated may be digitally signed by anunderwriter (e.g., PayPal) such that it may not be tampered with by acustomer. That is to say, if the data is tampered with, then the offerwill not work. The token works as a unique code/signature that ties theoffer to the customer such that customer targeting if available. Thus, acustomer unique identifier is added to the token so that only thedesignated customer may redeem it. For a customer that does not have anaffiliation with the financial institution, payment provider, merchantor the like, other tracking or unique identifiers may be added to thetoken. For example, the token may include, but is not limited to, asession identification number (ID), tracking ID, social media profile,etc., which can be used to uniquely identity the customer so that thetoken is not shared.

Prioritizing the offer at operation 518 enables the option to receivenotifications via email, messaging, application updates, site notices,and the like, that the offer is soon expiring. The process 500 may thencontinue again when a user is ready to use and checkout at which pointthe tokenized offer is presented and applied.

FIG. 6 illustrates an example computer system 600 in block diagramformat suitable for implementing on one or more devices of the system inFIG. 2. In various implementations, a device that includes computersystem 600 may comprise a personal computing device 102 (e.g., a smartor mobile device, a computing tablet, a personal computer, laptop,wearable device, PDA, etc.) that is capable of communicating with anetwork 626. A service provider and/or a content provider may utilize anetwork computing device (e.g., a network server) capable ofcommunicating with the network. It should be appreciated that each ofthe devices utilized by users 104, service providers, and contentproviders may be implemented as computer system 600 in a manner asfollows.

Additionally, as more and more devices become communication capable,such as new smart devices using wireless communication to report, track,message, relay information and so forth, these devices may be part ofcomputer system 600. For example, windows, walls, and other objects maydouble as touch screen devices for users 104 to interact with. Suchdevices may be incorporated with the systems discussed herein.

Computer system 600 may include a bus 610 or other communicationmechanisms for communicating information data, signals, and informationbetween various components of computer system 600. Components include aninput/output (I/O) component 604 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons,links, actuatable elements, etc., and sending a corresponding signal tobus 610. I/O component 604 may also include an output component, such asa display 602 and a cursor control 608 (such as a keyboard, keypad,mouse, touchscreen, etc.). In some examples, I/O component 604 mayinclude an image sensor for capturing images and/or video, such as acomplementary metal oxide semiconductor (CMOS) image sensor, and/or thelike. An audio input/output component 606 may also be included to allowa user 108 to use voice for inputting information by converting audiosignals. Audio I/O component 606 may allow the user 104 to hear audio. Atransceiver or network interface 622 transmits and receives signalsbetween computer system 600 and other devices, such as another userdevice, a merchant server, an email server, application serviceprovider, web server, a payment provider server, and/or other serversvia a network. In various embodiments, such as for many cellulartelephone and other mobile device embodiments, this transmission may bewireless, although other transmission mediums and methods may also besuitable. A processor 618, which may be a micro-controller, digitalsignal processor (DSP), or other processing component, that processesthese various signals, such as for display on computer system 600 ortransmission to other devices over a network 626 via a communicationlink 624. Again, communication link 624 may be a wireless communicationin some embodiments. Processor 618 may also control transmission ofinformation, such as cookies, IP addresses, images, and/or the like toother devices.

Components of computer system 600 also include a system memory component614 (e.g., RAM), a static storage component (e.g., ROM), and/or a diskdrive 616. Computer system 600 performs specific operations by processor618 and other components by executing one or more sequences ofinstructions contained in system memory component 612. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor 618 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and/or transmission media. Invarious implementations, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory such as system memorycomponent 612, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 610. In oneembodiment, the logic is encoded in a non-transitory machine-readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media include, for example, harddisk, magnetic tape, any other magnetic medium, CD-ROM, any otheroptical medium, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip orcartridge, or any other medium from which a computer is adapted to read.

Components of computer system 600 may also include a short rangecommunications interface 620. Short range communications interface 620,in various embodiments, may include transceiver circuitry, an antenna,and/or waveguide. Short range communications interface 620 may use oneor more short-range wireless communication technologies, protocols,and/or standards (e.g., WiFi, Bluetooth®, Bluetooth Low Energy (BLE),infrared, NFC, etc.).

Short range communications interface 620, in various embodiments, may beconfigured to detect other devices (e.g., primary device, secondarydevice, etc.) with short range communications technology near computersystem 600. Short range communications interface 620 may create acommunication area for detecting other devices with short rangecommunication capabilities. When other devices with short rangecommunications capabilities are placed in the communication area ofshort range communications interface 620, short range communicationsinterface 620 may detect the other devices and exchange data with theother devices. Short range communications interface 620 may receiveidentifier data packets from the other devices when in sufficientlyclose proximity. The identifier data packets may include one or moreidentifiers, which may be operating system registry entries, cookiesassociated with an application, identifiers associated with hardware ofthe other device, and/or various other appropriate identifiers.

In some embodiments, short range communications interface 620 mayidentify a local area network using a short range communicationsprotocol, such as WiFi, and join the local area network. In someexamples, computer system 600 may discover and/or communicate with otherdevices that are a part of the local area network using short rangecommunications interface 620. In some embodiments, short rangecommunications interface 620 may further exchange data and informationwith the other devices that are communicatively coupled with short rangecommunications interface 620.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 600. In various other embodiments of thepresent disclosure, a plurality of computer systems 600 coupled bycommunication link 624 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another. Modules described herein may be embodied in one ormore computer readable media or be in communication with one or moreprocessors to execute or process the techniques and algorithms describedherein.

A computer system may transmit and receive messages, data, informationand instructions, including one or more programs (i.e., applicationcode) through a communication link 624 and a communication interface.Received program code may be executed by a processor as received and/orstored in a disk drive component or some other non-volatile storagecomponent for execution.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readable media.It is also contemplated that software identified herein may beimplemented using one or more computers and/or computer systems,networked and/or otherwise. Where applicable, the ordering of varioussteps described herein may be changed, combined into composite steps,and/or separated into sub-steps to provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. For example, the aboveembodiments have focused on merchants and customers; however, a customeror consumer can pay, or otherwise interact with any type of recipient,including charities and individuals. Thus, “merchant” as used herein canalso include charities, individuals, and any other entity or personreceiving a payment from a customer. Having thus described embodimentsof the present disclosure, persons of ordinary skill in the art willrecognize that changes may be made in form and detail without departingfrom the scope of the present disclosure. Thus, the present disclosureis limited only by the claims.

What is claimed is:
 1. A system, comprising a non-transitory memorystoring instructions; a processor configured to execute the instructionsto cause the system to: receive, via a wireless connection, a requestfor presenting an offer to a user associated with a user deviceinteracting with a client site; determine, if the user associated withthe user device meets merchant restrictions; in response to determiningthat the user meets the merchant restrictions, transmit, via thewireless connection, a tokenized offer for display on the client site;receive, via the wireless connection, a request to save to a digitalwallet; and prioritize the tokenized offer based on priority informationincluded in token information received with the request.
 2. The systemof claim 1, wherein the executing instructions further causes the systemto: generate a notification to the user device indicating the expirationof the tokenized offer based on the priority information.
 3. The systemof claim 1, wherein a tokenized offer is not presented if the customerdoes not meet merchant restrictions.
 4. The system of claim 1, whereinthe executing instructions further causes the system to: confirm, upondetection of user checkout, that the user is a payment provider member;and onboard, the user if the user does not have a payment provideraccount.
 5. The system of claim 1, wherein the request to save to adigital wallet causes the tokenized offer to be saved locally on theuser device.
 6. The system of claim 1, wherein the offer is timesensitive and notifications are pushed to the user device indicating adeadline.
 7. The system of claim 1, wherein the executing instructionsfurther causes the system to: in response to the selection of the saveoffer button, reduce a monetary amount corresponding to the offerpresented from a campaign account.
 8. The system of claim 7, wherein thecampaign account is credited the monetary amount corresponding to theoffer if the offer expires.
 9. A method, comprising receiving, via awireless connection, a request for presenting an offer to a userassociated with a user device interacting with a client site;determining, if the user associated with the user device meets merchantrestrictions; in response to the determining that the user meets themerchant restrictions, transmitting, via the wireless connection, atokenized offer for display on the client site; receiving, via thewireless connection, a request to save to a digital wallet; andprioritizing the tokenized offer received based on priority informationincluded in token information received with the request.
 10. The methodof claim 9, further comprising: generate a notification to the userdevice indicating the expiration of the tokenized offer based on thepriority information.
 11. The method of claim 9, wherein a tokenizedoffer is not presented if the customer does not meet merchantrestrictions.
 12. The method of claim 9, further comprising: confirm,upon detection of user checkout, that the user is a payment providermember; and onboard, the user if the user does not have a paymentprovider account.
 13. The method of claim 9, wherein the request to saveto a digital wallet causes the tokenized offer to be saved locally onthe user device.
 14. The method of claim 9, wherein the offer is timesensitive and notifications are pushed to the user device indicating adeadline.
 15. The method of claim 9, further comprising: in response tothe selection of the save offer button, reduce a monetary amountcorresponding to the offer presented from a campaign account.
 16. Themethod of claim 15, wherein the campaign account is credited themonetary amount corresponding to the offer if the offer expires.
 17. Anon-transitory machine readable medium having stored thereon machinereadable instructions executable to cause a machine to performoperations comprising: receiving, via a wireless connection, a requestfor presenting an offer to a user associated with a user deviceinteracting with a client site; determining, if the user associated withthe user device meets merchant restrictions; in response to thedetermining that the user meets the merchant restrictions, transmitting,via the wireless connection, a tokenized offer for display on the clientsite; receiving, via the wireless connection, a request to save to adigital wallet; and prioritizing the tokenized offer received based onpriority information included in token information received with therequest.
 18. The non-transitory machine readable medium of claim 17,further comprising: generate a notification to the user deviceindicating the expiration of the tokenized offer based on the priorityinformation.
 19. The non-transitory machine readable medium of claim 17,wherein a tokenized offer is not presented if the customer does not meetmerchant restrictions.
 20. The non-transitory machine readable medium ofclaim 17, further comprising: confirm, upon detection of user checkout,that the user is a payment provider member; and onboard, the user if theuser does not have a payment provider account.